| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.9.2.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.9.2.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_9_2_1_Manage_Consultation_Requests_and_Responses |
| Title | CPS.9.2.1 Manage Consultation Requests and Responses (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide a means to capture and manage requests for consultation and responses. |
| Purpose | EHR system should support the ability to document and note calls made to physician/provider consultants, as well as their responses. This includes the time of the initial and any subsequent pages or calls, the time and method whereby the consultant responded, as well as the final disposition of the consultation. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide a means to capture and manage requests for consultation and responses.
EHR system should support the ability to document and note calls made to physician/provider consultants, as well as their responses. This includes the time of the initial and any subsequent pages or calls, the time and method whereby the consultant responded, as well as the final disposition of the consultation.
| CPS.9.2.1#01 | SHALL |
The system SHALL provide the ability to capture and maintain records of consultations by providers other than the attending provider. |
| CPS.9.2.1#02 | MAY |
The system MAY provide the ability to capture time notified (e.g., paged), time responded, and time arrived, as well as final disposition and recommendation of consultations. |
| CPS.9.2.1#03 | SHOULD |
The system SHOULD capture the details of the request for consultation and its responses as discrete data, including timestamps, sufficient for reporting. |
| CPS.9.2.1#04 | MAY |
The system MAY provide the ability to transmit from within the application, signals for electronic paging and dialing. |
| CPS.9.2.1#05 | SHOULD |
The system SHOULD provide the ability to present data on pending consultations. |
| CPS.9.2.1#06 | MAY |
The system MAY render to the referring provider a notification of the completion of consultations. |
| CPS.9.2.1#07 | MAY |
The system MAY present estimated time of arrival of consultants. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.9.2.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide a means to capture and manage requests for consultation and responses.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>EHR system should support the ability to document and note calls made to physician/provider consultants, as well as their responses. This includes the time of the initial and any subsequent pages or calls, the time and method whereby the consultant responded, as well as the final disposition of the consultation.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and maintain records of consultations by providers other than the attending provider.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture time notified (e.g., paged), time responded, and time arrived, as well as final disposition and recommendation of consultations.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD capture the details of the request for consultation and its responses as discrete data, including timestamps, sufficient for reporting.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to transmit from within the application, signals for electronic paging and dialing.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to present data on pending consultations.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY render to the referring provider a notification of the completion of consultations.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2.1#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY present estimated time of arrival of consultants.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.9.2.1",
"version" : "2.1.0",
"name" : "CPS_9_2_1_Manage_Consultation_Requests_and_Responses",
"title" : "CPS.9.2.1 Manage Consultation Requests and Responses (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide a means to capture and manage requests for consultation and responses.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "EHR system should support the ability to document and note calls made to physician/provider consultants, as well as their responses. This includes the time of the initial and any subsequent pages or calls, the time and method whereby the consultant responded, as well as the final disposition of the consultation.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-01",
"label" : "CPS.9.2.1#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture and maintain records of consultations by providers other than the attending provider."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-02",
"label" : "CPS.9.2.1#02",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture time notified (e.g., paged), time responded, and time arrived, as well as final disposition and recommendation of consultations."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-03",
"label" : "CPS.9.2.1#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD capture the details of the request for consultation and its responses as discrete data, including timestamps, sufficient for reporting."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-04",
"label" : "CPS.9.2.1#04",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to transmit from within the application, signals for electronic paging and dialing."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-05",
"label" : "CPS.9.2.1#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to present data on pending consultations."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-06",
"label" : "CPS.9.2.1#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY render to the referring provider a notification of the completion of consultations."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2.1-07",
"label" : "CPS.9.2.1#07",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY present estimated time of arrival of consultants."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.